Use UBI8 instead of SCL images#26072
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: yselkowitz The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
As big as this patch is, it seems it's a bit too piecemeal to succeed on its own. Looks like we're going to have to see if anything else can go in independently, otherwise it's just going to be a big branch merge. |
|
Make sure to have |
|
This is the complete upstreamable patchset. |
|
/test all |
|
openshift/ruby-hello-world#125 has merged |
|
/hold cancel |
|
/retest |
nodejs-10 is EOL. Also, use UBI8 image for ARM compatibility.
This is a follow-up from commit 1515f0c which removed the resulting file.
Where nodejs-mongodb-example was used, use nodejs-postgresql-example instead.
|
Sigh. |
|
Can anything be done to get this to merge? |
|
your last run at least failed with another previously reported, non build failure [sig-instrumentation][Late] Alerts shouldn't report any alerts in firing or pending state apart from Watchdog and AlertmanagerReceiversNotConfigured and have no gaps in Watchdog firing [Suite:openshift/conformance/parallel] I count 7 bugs associated with it at https://sippy.ci.openshift.org/?release=4.9 all of sig-builds pass the person who would have to override e2e-gcp-builds to at least get it on the merge queue would be the pillar lead, @bparees ... now, once on the merge queue, tests are reran and you are subject to more flakes if forced to guess, I would bet he would say you need to search on https://sippy.ci.openshift.org/?release=4.9 and either open bz's for non related failures like this, or the one I cited in #26072 (comment), or go to the existing bz's and post your failures runs, claim you are blocked in there, potentially raise the severity to try and get action sooner, etc. ... invariably it can be an exercise in patience I'm sure this is of little comfort, but this state of affairs with e2e's is not uncommon for a bit after master branch is opened up for a new release @bparees @adambkaplan of course please chime in if you see anything that needs to be corrected from your respective points of view with my guidance to @yselkowitz here |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest |
3 similar comments
|
/retest |
|
/retest |
|
/retest |
|
Looks like https://bugzilla.redhat.com/show_bug.cgi?id=1975283 is the issue of the day. Sigh... |
|
Filed openshift/kubernetes#825 as a first step, will then need to be revendored in origin. |
|
Filed #26264 as a draft to confirm the fix. Could I get some help with these please? |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
1 similar comment
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
@yselkowitz: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
There is a fairly strict process around propagating upstream k8s fixes down the openshift @yselkowitz There happens to be a active email thread in aos-devel http://mailman-int.corp.redhat.com/archives/aos-devel/2021-June/msg00108.html that was initiated by @soltysh where he provides a bunch of detail and lists a bunch of links explaining it. I personally have never done it so that is about as far as I'm comfortable going wrt coaching. Reaching out to @soltysh or the folks over at #forum-apiserver are probably your best source for help. On the plus side, you did get a e2e-gcp-builds that was able to avoid https://bugzilla.redhat.com/show_bug.cgi?id=1975283 ... at least there is some proof there. |
|
I'm not surprised, and I wasn't relishing the thought, but it is the natural conclusion of the advice you provided above. All I really want to do here is get THIS merged now in order to meet the deadlines that my team is under. |
Understood. fwiw I do see that https://bugzilla.redhat.com/show_bug.cgi?id=1975283 is on the agenda of the "OpenShift Mid-Sprint Check-in" on the aos main calendar at noon eastern today (https://docs.google.com/document/d/1ZC8LIEKohhiVN5i9nW-fWfLw37giyUUKoLyQfpe_CcI/edit#) google meet invite https://meet.google.com/pif-yqnk-aus?authuser=0&hs=122 |
|
/retest |
|
/override ci/prow/e2e-gcp This is known failure and it is unrelated to this change. |
|
@mfojtik: Overrode contexts on behalf of mfojtik: ci/prow/e2e-gcp DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
This test relies on pulling yaml from github rather than from bindata, which makes it difficult to pre-commit testing of changes which affect it. @akram and @gabemontero will move this to the jenkins client plugin E2E, but in the meantime, we comment it out. openshift#26072 (comment)
This test relies on pulling yaml from github rather than from bindata, which makes it difficult to pre-commit testing of changes which affect it. @akram and @gabemontero will move this to the jenkins client plugin E2E, but in the meantime, we comment it out. openshift#26072 (comment)
This test relies on pulling yaml from github rather than from bindata, which makes it difficult to pre-commit testing of changes which affect it. @akram and @gabemontero will move this to the jenkins client plugin E2E, but in the meantime, we comment it out. openshift#26072 (comment)
This allows tests to pass on other architectures, which do not have RHEL
7 and/or CentOS container content.
Goes together with openshift/ruby-hello-world#125
/cc @gabemontero @adambkaplan @soltysh @bparees